@dicej I recall we had a reason for locking the version - originally (fermyon/developer#1174) this block omitted the version (as this PR proposes), but I think there was a thing where it was picking up latest and that didn't work with the Spin of the time or something? We changed it in fermyon/developer#1233 to lock to a version, but the PR has no description and no linked issue. But both of this predate requirements.txt.

Do you recall the original issue? Is locking still relevant if someone is installing outside of requirements.txt (which seems to be what this block is covering)?

Which brings another question (for a separate PR) of should we move/remove this - I see there is a note saying "you don't need to do this if you're using requirements.txt" but I feel like readers will only see that after they've run the manual install...!

TLDR: if Joel is happy then I am happy

Looks like there are three options here:

1. pip3 install -r requirements.txt
2. pip3 install componentize-py==$BLESSED_KNOWN_GOOD_VERSION
3. pip3 install componentize-py

(or some combination of the above)

I'd vote for option 1 all by itself (i.e. remove the pip3 install componentize-py... part altogether). Option 2 would require updating the templates and the docs in lock-step or otherwise risk falling behind again. Option 3 would require updating componentize-py, the docs, and the templates in lock-step, and that sounds impractical to me.

Just using requirements.txt sounds good to me @dicej and @itowlson. I just updated the docs to just reference that installation path.